Repository navigation
fix: show component lifecycles on the home page - #152
Merged
Merged
Conversation
Replace the lifecycle-derived overall health percentage with labelled component counts and explicit loading, empty and unavailable states. Co-authored-by: OpenAI Codex <noreply@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The home page now shows component lifecycle counts from catalog metadata, replacing the misleading overall system-health percentage and health colours. The card explains its source, distinguishes loading, empty and unavailable data, and links to the component catalog.
Part of #85
Closes #151
Verified in this worktree
MISE_TRUSTED_CONFIG_PATHS="$PWD" mise run installpassed with existing peer-dependency warnings and no dependency or lockfile changes.MISE_TRUSTED_CONFIG_PATHS="$PWD" mise run lintpassed TypeScript and ESLint across all five workspaces.MISE_TRUSTED_CONFIG_PATHS="$PWD" mise run test -- --runInBand --verbosepassed 76 tests in 11 suites, with one existing skipped test and suite.BROWSER=none MISE_TRUSTED_CONFIG_PATHS="$PWD" mise run devcompiled successfully. The frontend and backend readiness endpoint both returned HTTP 200.git diff --check origin/main...HEADpassed.mise run buildwas not run locally because this is a frontend-only slice. The PR Build workflow runs all four mise gates, including the Docker image build, without publishing an image.Screenshot method (a) succeeded through the local Playwright CLI fallback, invoked via a temporary mise task. Paseo capture was blocked by "No browser automation host is connected". The browser and dev stack were stopped after verification.
Home-page viewport shows the surrounding layout at 1440x1200. The page uses an internal scroll area, so that capture is a viewport rather than the entire home-page content.
The five new regression cases passed
The verification transcript includes the timed test result block, lint output and browser capture commands. No catalog responses were mocked for the screenshots. The regression tests cover mixed lifecycle values that are absent from this local catalog snapshot.
Existing jsdom stylesheet and React/MUI warnings appeared in tests. Browser/dev warnings included the signals WebSocket 404, React deprecations and missing TechDocs search indexes. Those remain outside this slice. Lifecycle availability still follows the existing initial catalog request group; another failed request in that group makes the card unavailable rather than showing zero counts.
The parent epic stays open. Public-demo readiness and landing-page visual direction remain separate decisions.